Parallelize bare repo fetching and update existing worktrees on render#20
Merged
Parallelize bare repo fetching and update existing worktrees on render#20
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
flow renderusing goroutinesResetBranchto the gitRunnerinterface for hard-resetting worktreesWhy
Bare repo fetching was sequential, making render slow for multi-repo workspaces. More importantly, re-rendering a workspace with branches like
mainorstagingwould skip existing worktrees entirely, leaving them stale even though the bare repo had been fetched. Now render always picks up the latest remote state.Ref
Related to the recurring issue of stale cached git trees when starting new workspaces that reference remote branches.